Scripting > CygNet Scripting Guide > HyperPoint Scripting > Testing Scripts

Testing Scripts

Use the Simulation mode to test a HyperPoint’s script before putting it to use. This mode is independent of the server; it is a feature of CygNet Explorer. Therefore certain capabilities, such as accessing point data, are not enabled. For example, the message box command, MsgBox, will run in simulation mode for testing, but should not be used otherwise in HyperPoint Script. Also, breakpoints are only functional in simulation mode, and are not relevant in the HSS itself.

It is recommended that you test a HyperPoint on a non-production system to ensure that its script runs properly, then transfer it to a production system. If this is not possible, you can leave the Activate Script option on the point’s General page unchecked until it is ready for use.

Sometimes errors in script can cause other HSS points to fail, although the HSS may continue to run as normal. If the script engine is not performing as expected, check the log files and the ELS for possible warnings and errors (see Debugging and Error Handling).

Note: Two HyperPoints, ~SYHPEST and ~SYHPECT, come preinstalled in an HSS for health checking purposes. ~SYHPEST tracks the state of the script engine. ~SYHPECT is a counter that tracks script engine errors. One possible use of this point is automatically notifying an administrator when its value changes. For more information about setting up notifications, see Notifications.


Let us know how we can improve this topic.

CygNet at weatherford.com

© 2020 Weatherford. All rights reserved.